Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Addition of event_based_trips.txt to specification #527

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

jeffkessler-keolis
Copy link
Contributor

Draft PR to address #526

Example

Transit Agency X is running a special event train service to a football game starting at 7:00 PM with an estimated end time of 10:00 PM. There are two trains scheduled to leave the football stadium, both 30 minutes and 60 minutes after the game ends.

If the event ends early, the agency can accommodate passengers immediately, meaning that the first train can leave as early as 7:30 PM.

Due to federal rest restrictions, the final train must leave by midnight, and the prior train must leave by 11:45 PM. The latest the game can end while supporting the scheduled service pattern would be 11:00 PM for the second train, and 11:15 PM for the first train.

The first scheduled departure trip has trip_id trip_approx_1 and the second trip has ID trip_approx_2. Only passengers with a special event ticket are able to ride.

stop_times.txt

trip_id,arrival_time,departure_time,stop_id,stop_sequence,pickup_type,drop_off_type,timepoint
trip_approx_1,22:30:00,22:30:00,stadium,10,0,1,0
trip_approx_1,23:00:00,23:00:00,suburb,20,1,0,0
trip_approx_1,23:15:00,23:15:00,downtown,30,1,0,0
trip_approx_2,23:00:00,23:00:00,stadium,10,0,1,0
trip_approx_2,23:30:00,23:30:00,suburb,20,1,0,0
trip_approx_2,23:45:00,23:45:00,downtown,30,1,0,0

event_based_trips.txt

trip_id,event_end_approximate,event_end_earliest,event_end_latest,event_fares
trip_approx_1,22:00:00,19:00:00,23:00:00,1
trip_approx_2,22:00:00,19:00:00,23:00:00,1

Notes

  • stop_times.txt shows the approximate stop times for each trip, assuming that the event ends at its expected time.
    • By using stop_times.txt and the event_end_earliest and event_end_latest fields, one can determine the earliest and latest stop times for each trip.
    • Using the event_end_apprximate field, one can determine how long after the event each trip departs.
  • The event_end_latest field may not be the same between trips. For example, NJ Transit's River Line must do a short trip during late-night service due to track restrictions. Thus, a hypothetical event must have an earlier end time to support trips that cover the entire line.

Copy link

google-cla bot commented Dec 23, 2024

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant